Systems and methods for protecting information used by mobile devices

ABSTRACT

The present disclosure generally pertains to systems and methods for protecting information for use by mobile devices. In one exemplary embodiment, a system comprises a mobile device, a base, and a memory device. The mobile device has a user input interface, and the base is secured to a user. The mobile device is configured to receive data manually input via the user input interface by the user and to wirelessly transmit the data. The mobile device is further configured to wirelessly transmit a retrieval request in response to a user input. The memory device is mounted on the base. The memory device is configured to receive and store the data wirelessly transmitted by the mobile device. The memory device is further configured to retrieve the data and to wirelessly transmit the data to the mobile device in response to the retrieval request.

RELATED ART

Mobile devices, such as cellular telephones, lap-top computers, andpersonal digital assistants (PDAs), often store various types of data.For example, a user of a cellular telephone may input the telephonenumbers of contacts, such as friends, relatives, or business associates,whom the user frequently calls. Such data is typically stored in theuser's telephone so that a telephone number of desired contact can beautomatically retrieved and used to establish a telephone call withoutthe user having to later remember or input the telephone number.

However, if a mobile device is lost, stolen, or damaged, then the datapreviously entered into the device may be lost unless a backup copy iskept by the user. Unfortunately, maintaining a backup copy is somewhatburdensome, and many users enter data into mobile devices withoutstoring backup copies of such data elsewhere. In some cases, the usercan remember or otherwise acquire the lost information, but the processof re-entering the information into a new mobile device is burdensome.It would be desirable if the new mobile device could be automaticallyupdated to store the lost information without the user having tomanually input the data into the new mobile device.

In addition, the data stored in a lost or stolen mobile device may beconfidential or sensitive such that the user would prefer that a thirdparty could not access the data stored on the lost or stolen mobiledevice. To address these concerns, many mobile devices employ datasecurity features, such as user authentication, in an effort to preventunauthorized access of the data. However, these security features canoften be defeated by a hacker in order to gain access to protected data.To address this issue, some mobile devices are designed to purge itsdata in response to a determination that it has been lost or stolen. Forexample, once the user discovers that his mobile device is missing, suchuser may communicate a wireless signal instructing the mobile device topurge its data. In some cases, the detection of a lost or stolen mobiledevice is automatic so that the purging may occur even before the userdiscovers that the mobile device is missing. However, accurately makingsuch an automatic determination can be problematic. In addition,regardless of whether the lost or stolen determination is automatic, thedata is vulnerable until the mobile device is able to determine that ithas been lost or stolen.

Moreover, better techniques for protecting the data typically stored inmobile devices are generally desired.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure can be better understood with reference to the followingdrawings. The elements of the drawings are not necessarily to scalerelative to each other, emphasis instead being placed upon clearlyillustrating the principles of the disclosure. Furthermore, likereference numerals designate corresponding parts throughout the severalviews.

FIG. 1 is a block diagram illustrating an exemplary embodiment of asystem for protecting information used by mobile devices.

FIG. 2 is a block diagram illustrating an exemplary embodiment of amobile device, such as is depicted by FIG. 1.

FIG. 3 depicts a memory device, such as is depicted in FIG. 1, mountedon a finger ring.

FIG. 4 is a block diagram illustrating an exemplary embodiment of amemory device, such as is depicted in FIG. 1.

FIG. 5 is a block diagram illustrating an exemplary embodiment of asystem for protecting information used by mobile devices.

FIG. 6 is a flow chart illustrating an exemplary use of a system forprotecting information used by mobile devices, such as is depicted byFIG. 1.

DETAILED DESCRIPTION

Embodiments of the present disclosure generally pertain to systems andmethods for protecting information used by mobile devices that processdata, such as, for example, cellular telephones, lap-top computers,personal digital assistants (PDAs), and other like devices. In oneembodiment of the present disclosure, data used by a mobile device istransmitted to an external memory device that is secured to anauthorized user. The mobile device then purges such data in order tofrustrate attempts by hackers to access the data in the event that themobile device is lost or stolen.

While the mobile device is in the possession of the authorized user, themobile device can retrieve the data stored in the external memorydevice. Thus, the authorized user can access the data stored in theexternal memory system, but an unauthorized user who steals or finds themobile device likely cannot access the data stored in the memory device.Thus, the data is protected from unauthorized access in the event themobile device is lost or stolen, yet the data is preserved for futureuse by the authorized user. In this regard, after losing the mobiledevice, the user may use a second mobile device to access the datastored in the external memory device. Therefore, it is unnecessary forthe user to manually input the data into the second mobile device.

FIG. 1 depicts an exemplary embodiment of a system 20 for protectinginformation used by mobile devices. As shown by FIG. 1, the system 20comprises a mobile device 22, such as, for example, a cellulartelephone, lap-top computer, or personal digital assistant (PDA). Themobile device 22 comprises control logic 25, an antenna 27, a user inputinterface 31, a user output interface 33, and a power source 36, such asa battery, which provides electrical power to the other components ofthe device 22. The control logic 25 is configured to process data in anydesired manner, and such logic 25 is configured to communicatewirelessly with external devices via the antenna 27. For example, thecontrol logic 25 may be configured communicate voice data and/or othertypes of data with a cellular base station (not shown) via the antenna27. In another example, the control logic 25 may use the antenna 27 tocommunicate wirelessly with a WI-FI hot spot or some other externalcommunication network device or system.

The user input interface 31 allows a user to input data. For example,the user input interface 31 may comprise a keyboard, keypad, microphone,and/or some other input device for enabling a user to input data. Forexample, if the mobile device 22 is implemented as a cellular telephone,the user input device 31 may comprise a microphone for receiving voicedata that is communicated wirelessly via the antenna 27.

The user output interface 33 allows a user to receive data from themobile device 22. For example, the user output interface 33 may comprisea display device, such as a liquid crystal display (LCD), for displayingdata to the user and/or a speaker for playing audio messages to theuser. For example, if the mobile device 22 is implemented as a cellulartelephone, the user output device 31 may comprise a display device fordisplaying text messages and a speaker for playing voice data receivedvia the antenna 27 or other types of audio data.

Note that the control logic 25 may be implemented in hardware, software,or a combination thereof. FIG. 2 depicts an exemplary embodiment inwhich the control logic 25 is implemented in software and stored inmemory 42. When implemented in software, the control logic 25 can bestored and transported on any computer-readable medium for use by or inconnection with an instruction execution apparatus that can fetch andexecute instructions.

The exemplary embodiment depicted by FIG. 2 comprises at least oneconventional processing element 44, such as a digital signal processor(DSP) or a central processing unit (CPU), that communicates to anddrives the other elements within the device 22 via a local interface 47,which can include at least one bus. When at least a portion of thecontrol logic 25 is implemented in software, the processing element 44is configured to execute instructions of the logic 25.

As shown by FIG. 1, the system 20 also comprises a memory device 52 thatis external to the mobile device 22. In the exemplary embodiment shownby FIG. 1, the memory device 52 is mounted on a base 55, which issecured to a user. For example, in one exemplary embodiment shown byFIG. 3, the base 55 comprises a finger ring 56 on which the memorydevice 52 is mounted. In other embodiments, the base 55 may compriseother types of jewelry, such as a watch, bracelet, or necklace, worn bythe user or other types of objects worn or otherwise carried by theuser. For example, the base 55 may comprise a keyring that is typicallycarried in and possibly attached to a pants pocket, purse, or otherclothing item or personal accessory. In another example, base 55comprises a pair of eyeglasses worn by the user. Various other types ofobjects may be used to implement the base 55 in other embodiments.

In one exemplary embodiment, the memory device 52 is implemented on asingle integrated circuit (IC) chip in an effort to minimize the size ofthe device 52. Moreover, researchers at Hewlett-Packard (HP) Labs havedemonstrated a memory chip, referred to as the “memory spot,” which hasa length and width of just a few millimeters. Such a chip could be usedto implement the memory device 52. In other embodiments, other sizes ofthe memory device 52 and other numbers of IC chips are possible.

As shown by FIG. 1, the memory device 52 comprises control logic 63, anantenna 66, and memory 69, which is used to store data 72 transmittedfrom the mobile device 22, as will be described in more detailhereafter. If desired, the memory 52 may comprise a power source (notshown), such as a battery, to provide electrical power to the componentsof the device 52. In one exemplary embodiment, the memory device 52 useselectrical power from the signals received by the antenna 66 to power atleast one component of the device 52.

The control logic 63 of the memory device 52 may be implemented inhardware, software, or a combination thereof. FIG. 4 depicts anexemplary embodiment in which the control logic 63 is implemented insoftware and stored in memory 69. When implemented in software, thecontrol logic 63 can be stored and transported on any computer-readablemedium for use by or in connection with an instruction executionapparatus that can fetch and execute instructions.

The exemplary embodiment depicted by FIG. 4 comprises at least oneconventional processing element 84, such as a digital signal processor(DSP) or a central processing unit (CPU), that communicates to anddrives the other elements within the device 52 via a local interface 87,which can include at least one bus. When at least a portion of thecontrol logic 63 is implemented in software, the processing element 84is configured to execute instructions of the logic 63.

During operation, the user may input, to the mobile device 22, data 72that the user would like to have stored for later retrieval by themobile device 22. For example, if the mobile device 22 is a cellulartelephone, the user may input data 72 identifying various contacts andtheir respective telephone numbers. Such data 72 is used to call theidentified contacts. For example, when the user desires to place a callto one of the contacts, the data 72 is retrieved, and the telephonenumber of the identified person is used to place a telephone call. Othertypes of data 72 may be input by the user in other examples. Inaddition, the data 72 may be input via the user input interface 31 orotherwise received by the device 22. For example, the data 72 may bedownloaded from a network or remote communication device.

After the data 72 is input to the mobile device 22, the control logic 25of the mobile device 22 communicates the data 72 to the memory device52. In this regard, the data 72 is transmitted from antenna 27 toantenna 66. The control logic 63 of the memory device 52, upon receivingthe data 72 from antenna 66, stores such data 72 in the memory 69 forlater retrieval, as will be described in more detail hereafter. Afterthe data 72 is transmitted to the memory device 52, the control logic 25purges the data 72 from the mobile device 22. Therefore, if the mobiledevice 22 is lost or stolen, it does not contain the data 72 making itdifficult for a third party to access the data 72 upon finding or takingthe mobile device 22.

In this regard, the transmission range of the memory device 52 ispreferably limited. In one exemplary embodiment, the transmission powerfor the signals transmitted by the antenna 66 is sufficiently small suchthat the range of such signals is less than a meter (e.g., a fewcentimeters). Further, since the base 55 is secured to (e.g., worn by orattached to) the user, the data 72 cannot be transmitted from the memorydevice 52 to the mobile device 22 unless the device 22 is close to theuser, which is unlikely when the mobile device 22 is lost or stolen.More specifically, the data 72 cannot be transmitted from the memorydevice 52 to the mobile device 22 unless the mobile device 22 is withinthe transmission range of the memory device 52.

However, if the mobile device 22 is not lost or stolen, then it islikely that the mobile device 22 is within the transmission range of thememory device 52 when the user desires to access the data 72. In thisregard, when the user attempts to access the data 72 via the mobiledevice 22, the user is likely holding such device 22, and the mobiledevice 22 is, therefore, likely less than a few feet from the memorydevice 52 secured to (e.g., worn by or attached to) the user. In somecases, such as when the memory device 52 is mounted on a finger ring 56,the mobile device 22 may be only a few centimeters from the memorydevice 52. Moreover, when access to the data 72 is desired, the controllogic 25 of the mobile device 22 is configured to transmit, to thememory device 52, a retrieval request identifying the desired data 72.In this regard, the retrieval request is transmitted from antenna 27 toantenna 66. In response to the retrieval request, the control logic 63of the memory device 52 is configured to retrieve the data 72 identifiedby the retrieval request and to transmit the retrieved data to themobile device 22. In particular, the retrieved data 72 is transmitted byantenna 66 to antenna 27.

In one exemplary embodiment, radio frequency (RF) signals are used tocommunicate between the mobile device 22 and the memory device 52.However other types of signals may be used in other embodiments.

Upon receiving the retrieved data 72, the control logic 25 of the mobiledevice 22 uses the data 72 in a desired manner. After such use, thecontrol logic 25 may transmit the data 72, along with any updates, backto the memory device 52 for storage. After the mobile device 22 uses thedata 72, the data 72 is again purged from the device 22. However, if acopy of the data 72 remained in the external memory 69 and if the data72 is not updated by the mobile device 22, there is no need to transmitthe data 72 back to the memory device 52.

Accordingly, the data 72 is protected from unauthorized access in theevent that the mobile device 22 is lost or stolen. Note that suchprotection is automatic. In this regard, the data 72 is automaticallyprotected once the user walks far enough away from the mobile device 22such that the device 22 is outside the transmission range of the memorydevice 52, yet the user can access the data 72 if the user later findsthe mobile device 22. In this regard, upon finding and picking up themobile device 22, the device 22 should again be within the transmissionrange of the memory device 52. Accordingly, it is unnecessary for theuser to even discover that the mobile device 22 has been lost or stolenbefore the data 72 is protected from unauthorized access.

In addition, if the mobile device 22 is lost, stolen, or damaged, thenthe data 72 can be recovered even if the device 22 is never found or ispermanently damaged. In this regard, the user may use another device toaccess the data 72. For example, the user may purchase or otherwiseacquire a new mobile device to replace the one that was lost, stolen, ordamaged. The new device may be configured to access the data 72 from thememory device 52 in the same or similar way that the lost, stolen, ordamaged device 22 is configured to access the data 72. Thus, it isunnecessary for the user to re-enter the data 72 after losing ordamaging the device 22 that was used to originally input the data 72. Inthis regard, the new device may access the data 72 as may be desired.

In some embodiments, the security of the data 72 is further enhanced viaencryption. In this regard, before the data 72 is transmitted to thememory device 52, the control logic 25 of the mobile device 22 isconfigured to encrypt the data so that any third party intercepting thetransmission of the data 72 between antennas 27, 66 or otherwiseacquiring the data 72 is unable to effectively read it. In addition, thecontrol logic 63 of the memory device 52 may store the data 72 inencrypted form in the memory 69. In one exemplary embodiment, thecontrol logic 63 simply stores the received data 72 without decryptingit. Thus, if an unauthorized user steals or otherwise acquires the base55 and memory device 52, the unauthorized user should be unable toextract any useful information from the memory 69.

When the encrypted data 72 is retrieved and transmitted to the mobiledevice 22, the control logic 25 of the device 22 is configured todecrypt the data 72 before using it. Note that various known orfuture-developed encryption techniques may be used to encrypt the data72. In one exemplary embodiment, the memory device 52 is bound to manydevices so that devices other than one that originally encrypted thedata 72 can decrypt it. Therefore, if the mobile device 22 shown by FIG.1 originally encrypts the data 72 but is later lost, stolen, or damaged,another device that has been previously bound to the memory device 52can be used to decrypt the data 72 regardless of whether the lost,stolen, or damaged device 22 is ever found or repaired. However, otherdevices not bound to the memory device 52 cannot decrypt the data 72, oreven communicate with the memory device 52. Exemplary techniques forencrypting and decrypting the data 72 will be described below.

For illustrative purposes, assume that a first device 22′ (FIG. 5),referred to as the “root device,” originally encrypts and stores data 72to the memory device 52, but it is desirable for the memory device 52 tobe bound to another device 22″ so that this other device 22″ can accessthe data 72 in the event that the root device 22′ is lost, stolen, ordamaged. Also assume that each mobile device 22′, 22″ has a respectivepublic/private key pair. In this regard, assume that the root device 22′has a private key, referred to as “key_(priv1),” and a public key,referred to as “key_(pub1).” Also assume that the device 22″ has aprivate key, referred to as “key_(priv2),” and a public key, referred toas “key_(pub2).”

To encrypt the data 72, the root device 22′ generates a session key,referred to as “key_(session).” For example, the control logic 25′ ofthe root device 22′ may be configured to generate a random number anduse the random number as key_(session). The control logic 25′ thenencrypts the data 72 using key_(session). Any known or future-developedencryption scheme, such as Rivest-Shamir-Adleman (RSA) or AdvancedEncryption Standard (AES) encryption, may be used. The control logic 25′then transmits the encrypted data 72 to the memory device 52, whichstores the encrypted data 72.

To bind device 22″ to the stored data 72, the control logic 25′ of theroot device 22′ obtains the public key, key_(pub2), of the device 22″and an identifier of the device 22″. In this regard, the device 22″ maybe configured to transmit such information to the root device 22′. Thecontrol logic 25′ then encrypts key_(session) using key_(pub2) andtransmits the encrypted session key, referred to as “E(key_(session)).”The control logic 25′ transmits the identifier of device 22″ andE(key_(session)) to the memory device 52, and the control logic 63 ofthe memory device 52 stores the transmitted information in a table 99(FIG. 4).

Later, if it is desired for the device 22″ to access the data, such aswhen the root device 22′ is lost or stolen, the device 22″ retrieves theencrypted data 72 from the memory device 52. In this regard, the controllogic 25″ of the device 22″ transmits a retrieval request via antennas27″, 66, and the control logic 63 of the memory device 52 retrieves thedata 72 and transmits the retrieved data 72 to the device 22″ viaantennas 27′, 66. The control logic 63 also transmits the table 99 tothe device 22″. The control logic 25″ of the device 22″ searches thetable 99 for its identifier and the encrypted session key, i.e.,E(key_(session)), associated with such identifier. The control logic 25″then uses its private key, key_(priv2), to decrypt the encrypted sessionkey, E(key_(session)). After recovering key_(session), the control logic25″ uses key_(session) to decrypt the data 72.

Note that the data 72 may be bound to many other devices according tothe techniques described above. In this regard, for each bound device,the control logic 25′ of the root device 22′ encrypts key_(session) withthe public key of the device, and the encrypted session key is stored inthe table 99. Thus, any of the bound devices can use the table 99 torecover the session key and then use the session key to decrypt the data72.

Note that various data security techniques may be used to keepunauthorized users from accessing the data. For example, before the rootdevice 22′ binds another device to the data 72, the root device 22′ maybe configured to authenticate the other device via any knownauthentication algorithm. Various other security techniques may beemployed in yet other examples.

An exemplary use of the system 20 will now be described with particularreference to FIGS. 1 and 6.

For illustrative purposes assume that the mobile device 22 is a cellulartelephone and that the data 72 defines a contact list. In this regard,the contact list includes a list of telephone numbers that can beretrieved to make telephone calls via the device 22. Assume that eachtelephone number is associated with an identifier of the person orentity that would likely receive a call using the associated telephonenumber. For example, the identifier may be the name of such person orentity.

Further assume that the user of the device 22 desires to add an entry tothe contact list. In this regard, the user desires to update the contactlist to add a telephone number for a contact so that the telephonenumber can be automatically retrieved to make a call to the contact at alater time. Initially, the user selects an option indicating that a newcontact is to be added. Based on such input, the control logic 25 of thedevice 22 determines that data is to be input to the device 22, as shownby block 202 of FIG. 6. The user then inputs, via user input interface31, data indicative of the contacts telephone number and an identifier,such as the name, of the contact. As shown by block 206, the controllogic 25 receives such data and then wirelessly transmits the data tothe memory device 52, which is external to the device 22. However, thememory device 52 is mounted on a base 55 that is usually carried by theuser. For example, the base 55 may comprise a finger ring 56, as shownby FIG. 3, or other type of jewelry (e.g., a watch) that is typicallyworn by the user. In another example, the base 55 comprises a card,composed of plastic or some other material, that slides into a wallet ofthe user. In another example, the base 55 comprises a keyring that istypically carried in a pocket of clothes (e.g., pants) worn by the user.In other examples, the base 55 can comprise other types of devices.

Once the data is transmitted from the mobile device 22 to the memorydevice 52, the control logic 25 purges the data from the device 22, asshown by block 209. Upon receiving the data, the control logic 63 of thememory device 52 stores the data in the memory 69, as shown by block216. In the instant example, the control logic 63 updates the contactlist defined by the data 72 to add a new telephone number andidentifier. Such identifier is associated with the telephone number inthe data 72. For example, the contact list may be stored in a table witheach entry in the table having a telephone number and the identifierassociated with the telephone number.

In block 222, the control logic 25 of the mobile device 22 determineswhether data is to be retrieved from the memory device 52. If no data isto be retrieved, then the control logic 25 determines whether more data(e.g., a new contact for the contact list) is to be input, as shown byblock 227. If so, the process described above for inputting data andstoring such data in the memory device 52 is repeated.

At some point, assume that the user desires to call a contact whosecontact information is stored in the memory device 52. Thus, the userselects an option indicating that the user desires to access the contactlist. In response, the control logic 25 of the mobile device 22 makes a“yes” determination in block 222 and transmits a retrieval request tothe memory device 52. In response, the control logic 63 of the memorydevice 52 retrieves the contact list defined by the data 72 andwirelessly transmits the contact list to the mobile device 22, as shownby block 231. The control logic 25 of the mobile device 22 then uses theretrieved information, as shown by block 235. For example, the controllogic 25 may display the contact list via the user output interface 33.Upon viewing the contact list, the user selects the identifier ortelephone number of a person to be called. In response, the controllogic 25 of the mobile device initiates a cellular telephone call basedon the telephone number indicated by the data retrieved from the memorydevice 52. Upon using the contact list to make a call, the control logic25 purges the contact list from the mobile device 22, as shown by block242. Note that if the user updated the contact list before it is purged,the control logic 25 may transmit the update information to the memorydevice 52 so that the contact list in memory 69 can be updated asappropriate.

Since the data 72 that is input via the mobile device 22 is stored inthe external memory device 52 and purged from the mobile device 22, thedata 72 is protected against the risk of the mobile device 22 being lostor stolen. In this regard, the transmission range of the memory device52 is limited (e.g., less than a meter). Thus, in the event that themobile device 22 is lost or stolen, it is unlikely that the device 22will be within the transmission range of the memory device 52.Therefore, it is unlikely that an unauthorized third party with accessto the lost or stolen mobile device 22 can use such device 22 to accessthe data 72 stored in external memory 69. However, the original user ofthe device 22 can use another device to access the data 72 stored inexternal memory 69. For example, the user could buy a new cellulartelephone to replace the one that was lost or stolen and use the newcellular telephone to access the data 72 in the same manner describedabove that the mobile device 22 accesses the data 72.

Note that purging of the data 72 from the mobile device 22 isunnecessary in all embodiments. Not purging the data 72 generallyincreases the risk that an unauthorized third party can use a lost orstolen mobile device 22 to access the data 72. However, in suchembodiments, the memory device 52 essentially serves as a backup for thedata stored in the mobile device 22. Thus, if the mobile device 22 islost or stolen, the data 72 can be recovered from the memory device 52.

1. A system for protecting information for use by mobile devices,comprising: a mobile device comprising a user input interface, themobile device to receive contact data and to wirelessly transmit thecontact data, the mobile device to automatically purge the contact datafrom the mobile device after wirelessly transmitting the contact data toa memory device and the mobile device to wirelessly transmit a retrievalrequest in response to a user input; a base securable to the user; andthe memory device mounted on the base, the memory device to receive andstore the contact data wirelessly transmitted by the mobile device, thememory device to retrieve the contact data and to wirelessly transmitthe contact data to the mobile device in response to the retrievalrequest, the mobile device to display the contact data wirelesslytransmitted to the mobile device.
 2. The system of claim 1, the basecomprising a finger ring.
 3. The system of claim 1, the base comprisingjewelry.
 4. The system of claim 1, the contact data comprising at leastone contact, the at least one contact comprising at least one telephonenumber.
 5. The system of claim 1, the memory device to wirelesslytransmit the data to the mobile device via a radio frequency (RF)signal.
 6. The system of claim 1, the mobile device comprising acellular telephone.
 7. The system of claim 1, the mobile device toencrypt the contact data.
 8. The system of claim 7, the mobile device tobind the memory device to a second mobile device.
 9. A method forprotecting information for use by mobile devices, comprising: providinga mobile device, the mobile device comprising a user input interface anda user output interface; inputting contact data to the mobile device viathe user input interface; wirelessly transmitting the contact data fromthe mobile device to a memory device that is external to the mobiledevice; automatically purging the contact data from the mobile deviceafter the wirelessly transmitting the contact data from the mobiledevice to the memory device; storing the data in the memory device;securing the memory device to a user; receiving an input from the user;while the memory device is secured to the user, wirelessly transmittingthe contact data from the memory device to the mobile device in responseto the input; and displaying, via the user output interface, the contactdata wirelessly transmitted from the memory device to the mobile device.10. The method of claim 9, the input received via the user inputinterface.
 11. The method of claim 9, the memory device mounted on afinger ring.
 12. The method of claim 9, the memory device mounted onjewelry.
 13. The method of claim 9, the securing comprising insertingthe memory device into a pocket of clothes worn by the user.
 14. Themethod of claim 9, the wirelessly transmitting the contact data from thememory device to the mobile device comprising transmitting the contactdata via a radio frequency (RF) signal.
 15. The method of claim 9, themobile device comprising a cellular telephone.
 16. The method of claim9, further comprising encrypting the data.
 17. The method of claim 16,further comprising binding the memory device to a second mobile device.